Systems, apparatus and method for hosting and assigning domain names on a wide network

ABSTRACT

Embodiments of the instant invention are directed to a domain management system, apparatus and method for hosting and assigning domain names. Embodiments of the domain management system comprise a name assignment system and a hosting system, wherein the hosting system comprises a domain retrieval system and a data storage apparatus. The name assignment system verifies availability and assigns domain names to requesting clients. The name assignment system comprises an input component, a confirmation mechanism and a name storage means. Preferred embodiments of the domain retrieval system comprise a scheduler, a parsing member having a plurality of redirectors and a plurality of servers. The domain retrieval system locates the domain referenced by the domain name by parsing header information and utilizing a wildcard DNS. Once the domain is located, the domain retrieval system forwards the domain to the user computer.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/285,371, entitled System Apparatus and Method for Hosting andAssigning Domain Names on a Wide Area Network, filed Nov. 21, 2005,('371 application) which is herein incorporated by reference in itsentirety.

The '371 application is, in turn, a continuation of U.S. patentapplication Ser. No. 10/769,449, ('449 application) filed Jan. 29, 2004,now abandoned, which is herein incorporated by reference in itsentirety.

The '449 application is, in turn, a continuation of U.S. patentapplication Ser. No. 09/386,529 filed Aug. 30, 1999, which issued asU.S. Pat. No. 6,687,746, which is herein incorporated by reference inits entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the invention are directed to a system, apparatus andmethod for hosting domains and assigning domain names to users, whereinthe domain name is defined, in part, by the user. More specifically,embodiments of this invention create user assigned subdomain names bycombining the hosting domain name and the user name request such thatthe subdomain name resides within the zone file of the hosting domainname, that is, it resides at the same IP address.

2. Background Art

Wide area networks, such as the World Wide Web (“WWW”), or the Internet,are developing in importance both in commerce and in general methods ofcommunications among the population. Indeed, businesses advertise andsell products over the WWW. Internet businesses, which are exclusivelyvirtual businesses, that is, they exist only on-line, have become anacceptable modality of doing business. Similarly, individuals haveutilized the WWW for more effectively communicating with family andfriends.

The information made available on the WWW is located on a web site,wherein each web site is addressed by a domain name. Thus, to establisha web site, a user must obtain a domain name.

Currently, to obtain a domain name, the user, including individuals orbusiness owners, must acquire a fully qualified domain name, such as,www.domainname.com, or a shared domain name, such as,www.domainname.com/usersites/.about.mysiteaddress. Although thequalified domain name is the most desirable due to its relativeuniqueness and simplicity, qualified domain names are not only difficultto obtain, but are also, expensive. Thus, usually only persons, web hostproviders or entities acquire the fully qualified domain names.

Currently, any fully qualified domain name or variation thereof isassigned a unique Internet Protocol (“IP”) address. To provide an IPaddress for each domain or subdomain name, the provider must acquirelarge blocks of IP address block licenses. Unfortunately, these blocksof licenses are often unavailable, and even if available, are expensive.

In contrast to the fully qualified domain names, the shared domain namesare typically available at relatively low cost and can be obtained withrelative ease. Thus, the shared domain names are more advantageous anddesirable for individual users.

Despite the low cost and easy acquisition of shared domain names, shareddomain names are not necessarily user friendly. Indeed, most shareddomain names are complicated and cumbersome. Thus, users who desire asimple, professional and easy to remember domain name, instead acquiredifficult to remember and lengthy domain names.

In addition to the cumbersome nature of the shared domain names,categorization and/or prioritization of information on the WWW by searchengines and other modalities place shared domain name users at adisadvantage as domain names, such as, fully qualified domain names,that contain a desired search term are given greater weight in thesearch results. For example, www.news.com will probably be given apreferential position in a search result relative towww.mysite.com/users/.about.news. Thus, users utilizing a shared domainname are disadvantaged in maximizing and directing network users, ortraffic, to their web site.

When a user requests a qualified domain name, the domain name ismanually entered into a Domain Name System (“DNS”) database. Thedatabase must then be uploaded so that the database is updated on thenetwork server. Manual entry and the uploading of all of the newlyrequested domain names requires an enormous amount of personnel andtime. Thus, a web host provider, who desires to host thousands ofsubdomain names, must expend a large amount of resources simply to enterthe requested names into the system.

In addition to the expense of entering the newly requested domain names,providers of domain names experience further problems. For instance,most servers are not designed to effectively manage more than severalthousand domains. Indeed, these servers are incapable of arbitrarilyscaling domains, wherein scaling allows the servers to host a largenumber of domains than typically expected or capable of being hosted onthe server. To compensate for the inability to arbitrarily scale thedomain names, domain names are mapped to user directories. This mappingresults in inefficient server performance.

Further, the current system for distributing domain names results in DNSlatency time, that is, the time required for a new domain name entry topropagate throughout the WWW Currently, the latency time is typically 24to 72 hours (1-3 days).

A need in the industry exists for a system of hosting and assigningdomain names that is cost efficient and provides individual users withshorter and more memorable domain names. A further need exists for asystem that reduces the amount of time required to enter the new domainname into a database and further, which reduces the DNS latency suchthat domain names are more quickly introduced onto the wide areanetwork.

SUMMARY OF THE INVENTION

Embodiments of the instant invention are directed to a domain managementsystem, apparatus and method for hosting and assigning domain names.Embodiments of the domain management system comprise a name assignmentsystem and a hosting system, wherein the hosting system comprises adomain retrieval system and a data storage apparatus.

The name assignment system verifies availability and assigns domainnames to requesting users. The name assignment system comprises an inputcomponent, a confirmation mechanism and a name storage means, whereinthe user inputs a desired domain name into the input component. Thedesired name is confirmed or denied. If the request is approved, anassigned domain name, which includes the user's request as a portion ofthe name, is stored in a provider maintained name storage means.

Preferred embodiments of the domain retrieval system comprise ascheduler, a plurality of redirectors and a plurality of servers. Thedomain retrieval system locates the domain referenced by the domain nameby parsing header information and utilizing a wildcard DNS. Once thedomain is located, the domain retrieval system forwards the domain tothe user computer.

A feature of embodiments of the instant invention is that the assigneddomain names share an IP address with the hosting domain name. Anadvantage to this feature is that the web host provider is not requiredto acquire large number of address block licenses, thereby eliminatingsubstantial cost and dependency on availability of these address blocks.

Another feature of embodiments of the instant invention is that theservers are capable of scaling domain names. An advantage to thisfeature is that the servers are capable of managing virtually unlimitednumbers of domains.

Still another feature of embodiments of the invention is the eliminationof the need to update the DNS database. An advantage to this feature isthe reduction in web host provider costs for staffing personnel requiredto input the large number of domain names. A further advantage is thereduction in the delay time, or DNS latency time, of circulating newdomain names on-line.

Yet another feature of embodiments of the instant invention is that thedomain names assigned to the users are user friendly, that is, theassigned domain names are simple and easy to list. An advantage to thisfeature is that users, and network users, are more capable ofremembering the domain names and the simplicity of the name furtherincreases its recognition.

Still another feature of embodiments of the instant invention is thatthe user requested portion of the assigned domain names is prominentlypositioned in the domain name. An advantage to this feature is that theretrievability of the domain name by a search engine is increased.

The above and other features and advantages of embodiments of thisinvention will be apparent from the following more detailed descriptionwhen taken in conjunction with the accompanying drawings of illustrativeembodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description of embodiments of the invention will be madewith reference to the accompanying drawings, wherein like numeralsdesignate corresponding parts in the figures.

FIG. 1 is a network system environment in accordance with a preferredembodiment of the instant invention.

FIG. 2 is a block diagram of a name assignment system in accordance witha preferred embodiment of the instant invention.

FIG. 3 a is a sample web page illustrating a preferred embodiment of aninput component of the name assignment system of FIG. 2.

FIG. 3 b a sample web page illustrating a preferred embodiment of adomain name input member of the name assignment system of FIG. 2.

FIG. 4 is a preferred embodiment of portion of a DNS database, whereinthe provider domain name is stored utilizing a wildcard.

FIG. 5 depicts a preferred embodiment of the domain retrieval system.

FIG. 6 depicts a preferred embodiment of a frameset that is transmittedto the client's computer from the domain retrieval system of FIG. 5.

FIG. 7 is a block diagram of a preferred embodiment of the overallprocess of the domain name assignment and the retrieval of the domainassociated with the assigned domain name.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments of the instant invention are directed to a method andapparatus for hosting and assigning domain names on a wide area network.Embodiments of the instant invention employ a network of computers andprograms for assigning domain names and retrieving domains on a widearea network, such as, the WWW or the Internet.

Hardware Environment:

Preferred embodiments of the instant invention operate with a networkcomprising a plurality of networked computers, such as, for example, atleast one user computer and at least one provider computer which arecoupled together in a communications network, such as, for example, theInternet or WWW. FIG. 1 depicts a simplified representation of anexample network system 10 that is operated in accordance with preferredembodiments of the invention.

The network system 10 includes at least two client or user computers 12and at least one provider, or content, computer 14 coupled forcommunication therebetween by the remainder of the network, generallyrepresented at 16. In the illustrated embodiment, two client or usercomputers 12 and two content provider computers 14 are shown in thenetwork system. It will be understood that further embodiments mayemploy any suitable number of user and provider computers. The networksystem 10 may comprise a closed or intranet configuration, an open orpublic-access network configuration or combinations of suchconfigurations, as is well known in the art. For example, the user andprovider computers 12 and 14 may be included in smaller, interconnectednetworks which compose the overall network system 10. In an Internetembodiment, the network system comprises a combination of a large numberof interconnected internets and intranets. For purposes of simplifyingthe present disclosure, the various hardware components (for example,host servers, routers, connectors) and software necessary forcommunication between computers on the network system are not describedherein in detail. Such hardware and software are well within the scopeof one of ordinary skill in the art and are at least partially dependentupon the type of network system employed and the desired application ofuse.

The user computer 12 may comprise any suitable network device capable ofcommunicating with other network devices in the network system. Inpreferred embodiments, the user computer 12 comprises a programmableprocessor capable of operating in accordance with programs stored on oneor more computer readable media 18 (for example, but not limited tofloppy disc, hard disc, computer network, random access memory (RAM), CDRom, or the like), a display device 20 for providing a user-perceivabledisplay (for example, but not limited to visual displays, such ascathode ray tube CRT displays, light-emitting-diode LED orliquid-crystal-diode LCD displays, plasma displays or the like, audiodisplays or tactile displays), and a user input device 22 (for example,but not limited to, a keyboard, mouse, microphone, or the like). In onepreferred embodiment, the user computer comprises a personal computersystem having a CRT display, a keyboard and a mouse user-input device.

The user computer 12 is controlled by suitable soft are, includingnetwork communication and browser software to allow a user to request,receive and display information (or content) from or through a contentprovider computer 14 on the network system 10. In preferred embodiments,the user computer 12 employs a program, such as a browser, fordisplaying content received from a provider computer 14.

The content provider computer 14 may comprise any suitable networkdevice capable of providing content (data representing text, hypertext,photographs, graphics video and/or audio) for communication over thenetwork. In preferred embodiments, the provider computer comprises aprogrammable processor capable of operating in accordance with programsstored on one or more computer readable media 24 (for example, but notlimited to, floppy disks, hard disks, random access memory RAM, CD-ROM),to provide content for communication to a user computer 12. The providercomputer may comprise, for example, but not limited to, a personalcomputer, a mainframe computer, network computer, portable computer,personal data assistant (such as, a 3Com Palm Pilot), or the like. Theprovider computer 14 may include one or more internal data storagedevices (not shown) for storing content for communication to a usercomputer 12. Alternatively, or in addition, the provider computer 14 maybe coupled to an external data storage device, computer or other means,generally represented at 26, from which the provider computer 14 mayobtain content for communication to a user computer 12. In oneembodiment, the external device 26 may comprise a further network devicecoupled in the network 16.

In a preferred environment, the content provider computer 14 iscontrolled by suitable software to respond to a valid request forcontent by providing (or downloading) data in the form of one or moreHTML files to the user computer 12 from which the request was made. Itwill be understood by those skilled in the art that this processinvolves communications through suitable servers, routers and othercomponents, as is dictated by the particular network environment. TheHTML file(s) correspond to one or more HTML frames which, in conjunctionwith the browser software at the user computer 12, is displayable on thedisplay device at the user computer as text, hypertext, photographs,graphics, sound, or the like, in a form that is perceivable to the user.

GENERAL DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the domain management system comprise a name assignmentsystem 28 and a hosting system 62, wherein the hosting system 62comprises a domain retrieval system 64 and a data storage apparatus 66.

The name assignment system 28 verifies availability and assigns domainnames to requesting clients. The name assignment system 28 comprises aninput member 40, a confirmation means 42 (not shown) and a domain namestorage means 44 (not shown). With reference to FIG. 2, a user desiringto obtain a domain name enters a desired domain name 30 via the inputmember. Once entered, the provider computer 14 verifies the availabilityof the desired domain name 32 by the confirmation means 42. If theproposed domain name is not available, the user can enter anotherrequest 34. If however, the proposed domain name is available, thedomain name is entered in the name storage means 36.

The input member 40 is any mechanism that accepts information from theuser. In one embodiment, the input member 40 is a plurality of webpages.

With reference to FIGS. 3 a and 3 b, the input member 40 comprises aclient data input member 46 and a domain name input member 48. Theclient data input member includes a plurality of input windows 50 thatare configured to accept any type of provider defined information,including, but not limited to, a company name, the client's name, theclient's phone number, the client's E-mail address, and the client'spost office address. Once entered, the client information is stored onthe provider computer, by any suitable means, including, but not limitedto, a text file and a database.

The domain name input member 48 allows the client to customize a portionof a domain name. As is commonly understood, domain names can include aninfinite number of levels, however, domain names are usually limited toa particular number of levels for convenience. For instance, in oneembodiment, domain names can include a “top level”, “second level”,“third level” and “fourth level”. In a fully utilized domain name, thedomain name reads as follow: fourthlevel.thirdlevel.secondleveLtoplevel.It is to be understood that a domain name need not utilize all fourlevels, but can include any number of levels in an ascending order. Forinstance, the domain name can read, for example, as“secondlevel.toplevel” or “thirdlevel.secondlevel.toplevel”.

In preferred embodiments, the provider utilizes the toplevel andsecondlevel portions of the domain name for the provider chosen domainnames. However, it is to be understood, that the provider can define anynumber of name levels and this is not intended to limit the invention.The provider chosen domain names are stored in a DNS database. Inpreferred embodiments, the provider chosen domain names are stored witha wild card, such as, “*.providerdomainname.com”, wherein the wildcard,“*”, indicates that other levels may exist. Indeed, it is intended thatthese other levels be used by clients. FIG. 4 illustrates a sample DNSdatabase which includes a wildcard entry for a provider domain name“webjump.com”.

Embodiments of the instant invention utilize this domain name conventionin conjunction with the Wildcard DNS in allowing the clients to define aportion of their domain name. As stated above, the provider can defineany number of name levels. Depending upon how many of the name levelsare defined by the provider determines which name levels can be definedby the clients.

With reference to FIG. 3 b, the domain name input member 48 comprises aprovider domain name box 52, a site name input box 54, a client interestinput box 56, a proposed name box 58 and a submit button 60. The sitename input box 54 is a window, wherein the client inserts his desiredsite name. The portion of the domain name chosen by the client as thesite name is the third level domain name.

The client interest input box 56 is a window that allows the client tofurther define his domain name. For instance, in one embodiment, theclient can input his profession or an interest. This information isadded to domain name at the fourth level.

The information input by the client is added to the provider domainname. Once the client has input either the sitename, or the sitename andan interest, a proposed domain name is presented to the client in theproposed name box 58 based upon his input. For instance, if the clientonly inputs a sitename, the proposed domain name is“sitename.providerdomainname.com”. Similarly, if the client inputs asitename and an interest, the proposed domain name is“sitename.interest.providerdomainname.com”. If the proposed domain nameis acceptable to the client, the client submits the proposed domain nameto the provider computer via depressing the submit button 60, or by anyother means capable of transmitting the proposed name to the providercomputer.

Upon submission, the proposed domain name is transmitted to theconfirmation member. The confirmation member is a program that searchesthe domain name storage means for the proposed domain name. In onepreferred embodiment, the domain name storage means is a register of allof the client assigned domain names, which is maintained by providercomputer 14. The confirmation member is capable of quickly searching thedomain name storage means or register as the toplevel and secondlevelportions of the domain is constant and the program is only required toreview the thirdlevel, and in some instances, the fourthlevel. In onepreferred embodiment, the program for searching the register is writtenin Active Server Pages (“ASP”) language, although any programminglanguage, including, but not limited to, C++, Visual Basic (“VB”) andPerl are suitable.

After the provider computer determines whether the requested domain nameis available, the provider computer 14 notifies the client of theresults. If the requested domain name is available, the providercomputer 14 notifies the client that the domain name is accepted. Theprovider computer 14 notifies the client of the availability of therequested name, by any suitable means, including, but not limited to,posting a message on the client's computer 12, electronic mail service,postal service and telephone service. In one preferred embodiment, theconfirmation is posted on a web page on the client's computer 12 so thatthe client has virtually instantaneous confirmation or denial. If therequest is denied, the client is able to input another request. Afterthe new domain name has been assigned to the client, the newly assigneddomain name is automatically stored in the domain name memory means thatis, the provider maintained register is updated. As the providermaintains a register of assigned names, there is no need to update theDNS database and therefore, no requirement to reload the DNS database.Indeed, the DNS database is only updated if a new provider chosen domainname is added.

It is to be understood that the above described embodiment is notintended to limit the invention. For instance, in other embodiments, theinput of the client data and the preferred domain name by the clientneed not be accomplished via a client computer. Rather, the client couldutilize any suitable means of identifying a preferred domain name,including, but not limited to, telephone services and postal services.In this embodiment, the provider would verify the availability of theclient's requested domain name and the assignment of the name would beentered and recorded as described above. In still a further embodiment,the provider distributes the domain names by any suitable means,including, but not limited to, an auction. In an auction environment,the provider receive bids from clients, wherein the domain name isassigned to the highest bidder. In this manner, the name assigned to thehighest bidding client would be recorded in accordance with theembodiments described above.

As indicated above, the hosting system 62 comprises a domain retrievalsystem 64 and a data storage apparatus 66. The hosting system 62operates in conjunction with the name assignment system 28 discussedabove.

When any network user, including a client, enters a request into thebrowser for an assigned domain name, such as, for example,http://sitename.webjump.com, the DNS resolves the requested domain nameto its Virtual Internet Protocol (“VIP”) address. By default, incomingbrowser requests for any subdomain to “providerdomainname.com” isforwarded to the host VIP address for the domain“providerdomainname.com”. This is achieved by including the wildcardentry into the domain's zone file in the form of“*.providerdomainname.com” as shown in FIG. 4 for webjump.com. Thus,instead of the zone file including all possible subdomain names, suchas, “sitename.providerdomainname.com”, wherein each subdomain would haveits own IP address, the request is directed to the address of thewildcard entry “*.providerdomainname.com”. For example, in oneembodiment, the domain name “sitename.webjump.com” resolves to216.49.10.200, wherein “webjump.com” is the provider chosen domain name.The resolved VIP address is then transmitted to the domain retrievalsystem.

With reference to FIG. 5, a preferred embodiment of the hosting system62 comprising a domain retrieval system 64 and a data storage apparatus66. The domain retrieval system 64 comprises a scheduler 68, a pluralityof redirectors 70 and a plurality of servers 72. Upon resolution of theVIP address, the VIP address is transmitted to the scheduler 68. Thescheduler 68 is a traffic director that load balances the requested VIPaddress across the plurality of redirectors 70. Although any mechanismto load balance network user requests is suitable, in one preferredembodiment, a scheduler, manufactured by Resonate, is utilized.

The redirectors 70 are servers which include a parsing mechanism. In oneembodiment, the plurality of redirectors 70 comprises a first redirectorR1, a second redirector R2 and a third redirector R3. It is to beunderstood that the number of redirectors is not intended to be limitedand embodiments can include more or less than three redirectors.

Prior to transmitting the request, the scheduler 68 chooses a particularredirector to receive the request, wherein the redirector that receivesthe request is determined by the current load on the particularredirector. For example, if the load on the first redirector and thethird redirector is 80%, and the load on the second redirector is 20%,the scheduler passes the request to the second redirector R2.

Upon receipt of the request by the redirector, in this example,redirector R2, the parsing mechanism parses the URL request of theclient or network user and translates the request into a predefinedprovider subdomain and a client directory. Each predefined providersubdomain identifies a provider chosen domain name utilized in theclient assigned domain names. For instance, in one embodiment, a seriesof subdomains are called “freehosting.at.*”, wherein theproviderdomainname.com is substituted for the wildcard. Thus, for theprovider chosen domain name “weojump.com”, the subdomain is“freehosting.at.webjump.com”. The identification of the toplevel andsecondlevel portion of the requested domain name identifies theappropriate subdomain to be referenced. It is to be understood that anIP address of the subdomain can also be used to identify the providerchosen domain.

In addition to identifying the subdomain from the request, the parsingmechanism removes the site name from the Hypertext Transfer Protocol(“HTTP”) header information of the request, wherein the site nameidentifies the appropriate directory on the subdomain. In one preferredembodiment, the HTTP version 1.1 header content information is utilized.Once the appropriate directory is determined, the HTTP request isdirected to the appropriate directory within the provider file system,thereby mapping URLs to the provider file system directory structure.For example, “sitename.webjump.com” translates to the directory offreehosting.at.webjump.com/si/sitename-webjump, wherein the directoriessi/sitename-webjump are defined by the particular site name. It is to beunderstood that any directory naming convention can be used and this isnot intended to be limiting.

Once the parsing of the address is complete, the redirector transmits anempty frameset 74 to the client computer 12, wherein the frameset 74includes a plurality of frames. With reference to FIG. 6, the frameset74 is provider defined and includes a client frame 76 and a plurality ofprovider frames 78. The client frame 76 is typically the larger of theframes and represents the space within which the client's informationwill be contained.

The provider frames 78 represent the predefined space wherein theprovider will add information. The provider frames 78 include, but arenot limited to, advertising information, revenue information andnavigation information. In one embodiment, provider frames 78 are notincluded in the frameset 74, rather, only a client frame 76, or frames,are transmitted to the client computer 12.

In response to the receipt of the frameset 74, the user computer 12requests the Uniform Resource Locator's (“URL's”) for the various framescontained within the frameset 74 from the provider computer 14. Therequest for the client frame 76 is resolved to the VIP address of thesubdomain by DNS. For example,“freehosting.at.webjump.com/si/sitename-webjump/” resolves to216.49.10.245. Similarly, the request for the provider frame 78 isresolved to a VIP address. For example, URLs for the provider computer,bannervip.webjump.com/webjump/revenue_ad.asp andbannervip.webjump.com/webjump/house_ad, resolves to 216.49.10.236. Theseaddresses are then transmitted to the scheduler 68.

In turn, the scheduler 68 load balances the VIP addresses across theplurality of servers 72. With reference again to FIG. 5, in preferredembodiments, the servers 72 comprise a plurality of web servers 80 and aplurality of provider servers 82. The frame URL associated with theclient files are requested by the user computer 12 to the web servers80. Similarly, the frame URL associated with the provider files arerequested by the user computer to the provider servers 82.

The web servers 80 access the data storage array 66 for the requestedinformation. The data storage array 66 is a NetApp F76P, although anystorage means capable of storing data files, including, but not limitedto, hard disk and tape, is suitable. The information from the providerserver 82 and the content server 80 that corresponds to the URLs istransmitted to the user computer such that the frames in the frameset 74are displayed with information.

With reference to FIG. 7, in operation, the domain management systemfacilitates the assignment of domain names to clients and the retrievalof the domains referenced by those domain names. To set up a domainname, a client enters the network 84 and accesses the providercomputer's domain management system 86, in particular, the nameassignment system, or sign-up page. The client enters a desired name forthe third and, in some instances, the fourth level portion of the domainname. Once the client has successfully been assigned a name, the domainname is stored on the provider computer in, for example, a register, atext file listing or a catalog, although any manner of compiling theassigned domain names is suitable. No updating of the DNS database isrequired.

The client now determines the content he desires to include on his newlyassigned domain and transfers that data to the provider computer by anysuitable means, including, but not limited to, file transfer protocol(“FTP”) and HTTP. The content of the domain is now referenced by itsdirectory on the provider's data storage array 66.

When the client desires to retrieve his domain, or wide area network, orremote, users desire to visit the web site, the client/users access thenetwork 16. The client/user then submits a request for the desireddomain 94 which is transferred from the user computer to the providercomputer. The provider computer directs the request to the domainretrieval system 96 which translates the request to a provider definedsubdomain name a client directory contained on that subdomain 98. Oncethe request is translated, the provider computer sends the user computeran empty frameset 100, wherein the frameset 74 includes a plurality offrames. The user computer, in turn, requests the data that is intendedto occupy the frames in the frameset 102. The provider computer 14 thenlinks the data request with the content server 80 and the providerserver 82. The content server 80 accesses data storage containing theclient's data associated with the domain name and transmits the data tothe appropriate frame in the frameset 104. Similarly, the providerserver transmits the appropriate provider information to the appropriateframe in the frameset 104.

As shown from above, embodiments of the domain management system providea friendly system by which clients can partially define their domainnames and receive a domain name that is memorable and that increases theclient's ability to direct traffic to the domain.

Indeed, in embodiments of the instant invention, the assigned-domainname places the client designated portion first such that the client'sname is prominent. Further, as the client is permitted to choose a thirdor fourth level domain names, the clients can more accurately choosetheir domain name so as to more effectively direct traffic, that is,direct other users to a specific site which is referenced by the domainname. For example, a provider may designate a third level domain“dogs.webjump.com” as a domain directed to dog-related sites. The clientcould then choose a fourth level of the domain name, “bobspuppystore”,such that the domain name assigned to the client is“bobspuppystore.dogs.webjump.com”. By utilizing the general category of“dogs”, the client can direct network users having a dog interest to hissite advertising the puppy store. In this manner, the client has moreeffectively utilized the domain name to direct pertinent traffic to hissite.

Further, embodiments of the domain management system provide theprovider host with the ability to scale domains such that the serverscan host a virtually unlimited number of domains as there is norequirement for a unique IP address for each subdomain. Indeed, the useof the wildcard DNS allows unlimited subdomain names to be created foreach domain on the servers. In this manner, the servers are capable ofreferencing a virtually unlimited number of subdomains. The ability toscale domains decreases labor and material costs. Further, the use ofthe wild card DNS to denote domain names increases the expediency withwhich a newly assigned domain name can be propagated throughout thenetwork as the newly assigned name is stored in a provider maintainedregister and is referenced by the VIP address of the wildcard providerdomain name stored in the DNS database. The use of the providermaintained register eliminates the need to update the DNS database.

Although the foregoing described the invention with embodiments havingparticular forms that have been illustrated and described, this is notintended to limit the invention. Rather, the foregoing is intended tocover all modifications and alternative constructions falling within thespirit and scope of the invention as expressed in the appended claims.

1-39. (canceled)
 40. A method comprising: receiving, by a host computing device, a content request comprising a requested address, wherein the requested address comprises: a host name corresponding to the host computing device, and a content label; determining a content address comprising a provider subdomain and a content directory corresponding to the content label; and providing the content address in response to the content request.
 41. The method of claim 40, wherein the content label is located in a wildcard portion of the requested address.
 42. The method of claim 40, wherein the determining the content address comprises: searching a database for a content address corresponding to the content label, the database comprising a plurality of additional labels each related to a corresponding content address; retrieving content from a content storage system using the content address; and serving the content in response to the content request.
 43. The method of claim 41, further comprising: configuring a DNS database to direct the content request, irrespective of the content label in the wildcard portion of the requested address, to the host computing device.
 44. The method of claim 40, further comprising: receiving the content for storage on a content storage system from a device authenticated with the content label.
 45. The method of claim 40, further comprising: receiving a request to register the content label; and registering the content label in the database.
 46. The method of claim 45, wherein the receiving the request to register the content label further comprises: receiving a request to register the content label under the host name, wherein the host name is selected from a list of available host names configured in a DNS database.
 47. A computer-readable storage device having computer program logic recorded thereon, execution of which, by a computing device, causes the computing device to perform operations comprising: receiving a content request comprising a requested address, wherein the requested address comprises: a host name corresponding to a host computing device, and a content label; determining a content address comprising a provider subdomain and a content directory corresponding to the content label; and providing the content address in response to the content request.
 48. The computer-readable storage device of claim 47, wherein the content label is located in a wildcard portion of the requested address.
 49. The computer-readable storage device of claim 47, wherein the determining the content address comprises: searching a database for a content address corresponding to the content label, the database comprising a plurality of additional labels each related to a corresponding content address; retrieving content from a content storage system using the content address; and serving the content in response to the content request.
 50. The computer-readable storage device of claim 48, the operations further comprising: configuring a DNS database to direct the content request, irrespective of the content label in the wildcard portion of the requested address, to the host computing device.
 51. The computer-readable storage device of claim 47, the operations further comprising: receiving the content for storage on a content storage system from a device authenticated with the content label.
 52. The computer-readable storage device of claim 47, the operations further comprising: receiving a request to register the content label; and registering the content label in the database.
 53. The computer-readable storage device of claim 52, wherein the receiving the request to register the content label further comprises: receiving a request to register the content label under the host name, wherein the host name was selected from a list of available host names configured in a DNS database.
 54. A system comprising: a memory configured to store instructions comprising: instructions to receive a content request comprising a requested address, wherein the requested address comprises: a host name corresponding to a host computing device, and a content label, instructions to determine a content address comprising a provider subdomain and a content directory corresponding to the content label, and instructions to provide the content address in response to the content request; and one or more processors configured to process the instructions.
 55. The system of claim 54, wherein the content label is located in a wildcard portion of the requested address.
 56. The system of claim 54, wherein the instructions to determine the content address comprise: instructions to search a database for a content address corresponding to the content label, the database comprising a plurality of additional labels each related to a corresponding content address, instructions to retrieve content from a content storage system using the content address, and instructions to serve the content in response to the content request.
 57. The system of claim 55, the instructions further comprising: instructions to configure a DNS database to direct the content request, irrespective of the content label in the wildcard portion of the requested address, to the host computing device.
 58. The system of claim 54, the instructions further comprising: instructions to receive the content for storage on a content storage system from a device authenticated with the content label.
 59. The system of claim 54, the instructions further comprising: instructions to receive a request to register the content label, and instructions to register the content label in the database.
 60. The system of claim 59, wherein the instructions to receive the request to register the content label comprise: instructions to receive a request to register the content label under the host name, wherein the host name was selected from a list of available host names configured in a DNS database.
 61. A system comprising: a host computing device configured to receive a content request comprising a requested address, wherein the requested address comprises: a host name corresponding to the host computing device, and a content label; and a redirector configured to determine a content address comprising a provider subdomain and a content directory corresponding to the content label and to provide the content address in response to the content request.
 62. The system of claim 61, wherein the content label is located in a wildcard portion of the requested address.
 63. The system of claim 61, wherein the redirector is further configured to search a database for a content address corresponding to the content label, the database comprising a plurality of additional labels each related to a corresponding content address, to retrieve content from a content storage system using the content address, and to serve the content in response to the content request.
 64. The system of claim 62, further comprising: a DNS database configured to direct the content request, irrespective of the content label in the wildcard portion of the requested address, to the host computing device.
 65. The system of claim 61, further comprising: a content storage system configured to receive the content for storage from a device authenticated with the content label.
 66. The system of claim 61, wherein the host computing device is further configured to receive a request to register the content label and to register the content label in the database.
 67. The system of claim 66, wherein the host name was selected from a list of available host names configured in a DNS database. 